1 link tagged with all of: sean goedecke + software design + databases + coupling + architecture
Click any tag below to further narrow down your results
Links
Sean Goedecke argues that database rows are effectively global variables, which clashes with the common advice to avoid globals. He tests five explanations for why databases get a pass and concludes that explicitness and disciplined usage, not anything inherent to databases, are what make them tolerable.
- Databases share the two core problems of global variables: any part of a program can read or write any record, and different parts become implicitly coupled through shared state.
- Many proposed reasons databases are better fail under scrutiny. ACID guarantees don't fix the core problem, and wrapping a global in a mutex doesn't make it acceptable.
- The two reasons he finds convincing are that database queries are explicit (they need a connection and a query call) and that teams use databases for a narrow set of purposes. Both are conventions, not inherent traits, so a codebase could apply them to globals too.